<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title>Velocitime Minutes</title>
  <meta http-equiv="content-type"
 content="text/html; charset=ISO-8859-1">
  <meta name="author" content="robert">
</head>
<body>
<h1>Velocityme Minutes 48<br>
</h1>
<table border="1" cellpadding="2" cellspacing="0" width="100%">
  <tbody>
    <tr>
      <th bgcolor="#cccccc" valign="top">Date<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Venue<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Present<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Apologies<br>
      </th>
    </tr>
    <tr>
      <td valign="top">2004-11-23<br>
20h20-21h55<br>
      </td>
      <td valign="top">22 Bordeaux<br>
Tokai Villas<br>
      </td>
      <td valign="top">Robert Crida (RC)<br>
Barry Radloff (BR)<br>
      </td>
      <td valign="top"><br>
      <br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<table style="width: 100%;" border="1" cellpadding="2" cellspacing="0">
  <tbody>
    <tr>
      <th
 style="vertical-align: top; background-color: rgb(204, 204, 204);"
 colspan="2">Topic<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Responsible Person<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Due Date<br>
      </th>
    </tr>
    <tr>
      <td style="vertical-align: top;">1.<br>
      </td>
      <td valign="top"><b>Minutes from meeting 41</b><br>
      </td>
      <td valign="top"><br>
      </td>
      <td valign="top"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td valign="top">The minutes have not yet been written, BR trying
to find notes<br>
      </td>
      <td valign="top">BR<br>
      </td>
      <td valign="top">2004-12-07<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">2.<br>
      </td>
      <td style="vertical-align: top;"><span style="font-weight: bold;">Minutes
from meeting 47</span><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">The minutes were delivered by BR
at the meeting and accepted.<br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">3.<br>
      </td>
      <td style="vertical-align: top; font-weight: bold;">Requirements
for discussion with Philip Robinson (PR)<br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">RC compiled following list
suggesting environment types which are well suited to Velocityme:<br>
      <ul>
        <li>Many, compilcated projects - eg IT, construction</li>
        <li>Large teams with complicated relationships - keeps track of
information passing between many people</li>
        <li>Process driven organisation - eg ISO9001. Note could we
identify industry standard configurations or requirements, possibly by
approaching an ISO auditor?</li>
        <li>Many reasonably similar, but separate, projects - helps
keep track of individual states and changes etc</li>
        <li>Management who want to keep track of progress - could use
issue track but probably needs planning functionality.</li>
      </ul>
The following environments are less suitable for Velocityme<br>
      <ul>
        <li>Large numbers of isolated cases - eg help desk for bank,
insurance. Velocityme could be tailored to work better with this but it
doesn't exploit the information structure benefits (hierarchy,
inappropriate organisation info - too much)</li>
        <li>Individuals solving single large projects - in this case
the developer tends to keep most of the information at their fingertips
and their is hence less benefit in using an automated tool. In this
case there is still an advantage as it provides a long term store and
can be used to instill discipline.</li>
        <li>Companies with a lack of process - doesn't take advantage
of the workflow feature although one can create very simple task types
and roles to minimise setup and overhead, at the cost of reduced
usefulness of the captured data.<br>
        </li>
      </ul>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">RC started reviewing web to find
competitors and who their customers are and what they are charging etc.
The following findings have been made thus far:<br>
      <ul>
        <li>Competitors reports customers from practically any field
you can imagine but their tools are probably used primarily by the IT
departments within each of the customer organisations. Didn't come
across anything clearing indicating issue tracking being used for
anything else except perhaps call centres.</li>
        <li>Combination of service companies and people selling
software.</li>
        <li>Appears that the primary mechanism for reaching new
customers is through the web sites, especially for the smaller
companies. No indication of anything else visible.<br>
        </li>
      </ul>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">On the financial side, RC has
already previously compiled a potential pricing document. The following
points are relevant:<br>
      <ul>
        <li>Installation could require the following steps which each
have an overhead for us when done at a client site - installing or
configuring Apache, installing JBoss, adapting to client database and
setting up account for velocityme, working with Microsoft IIS (MS
equivalent of Apache), travelling costs for visiting site.</li>
        <li>Remote installation will require documentation to help the
client perform the above steps</li>
        <li>Remote administration will require that the client has
velocityme available on the internet and that we would have a permanent
login with administrative rights which may be deemed risky by client.
Time charge.<br>
        </li>
        <li>If the client does not have internet connection then
administration will require travel to site plus time overhead.</li>
        <li>Support also consists of helping client to configure their
systems for their particular requirements. This can be done with
standard downloads (not yet supported) or a fair degree of consultation
(probably around 1-2 days per client) to identify roles and task types.</li>
        <li>Probably need to be able to present training seminars.</li>
        <li>How stable does our company look for providing after sales
service - what would we commit? find separate support company?<br>
        </li>
      </ul>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">The following potential markets
for Velocityme were considered:<br>
      <ul>
        <li>IT - most obvious candidate. Barriers including competition
from existing tools. Common barrier for all markets is overcoming
culture of not using these tools. Easiest path may be via companies who
already use tools but are disatisfied - porting database may be a
useful option in this case?</li>
        <li>Property Administration - Would probably provide an
administered service and could probably standardise the setup quite a
bit. Not sure if the usage model is quite right, more like separate
individual cases.</li>
        <li>Construction - Would probably be more of a planning tool,
doubt that it would be used by more than a handful of
managers/engineers. Needs further investigation.</li>
        <li>Event organisers - Probably most useful for planning and
preparation but not for execution due to relatively short time-frame.</li>
        <li>ISO auditors - should be approached for comment at least.
If we could say that developed with their input it would probably be
good. Perhaps they could even promote Velocityme?</li>
        <li>Test and Data Services - Should be approached to find out
if Velocityme could compliment their existing service?<br>
        </li>
      </ul>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">4.<br>
      </td>
      <td style="vertical-align: top; font-weight: bold;"><span
 style="font-weight: normal;">BR to contact Linux chat groups to elicit
response from potential partners for offering support services</span><br>
      </td>
      <td style="vertical-align: top;">BR<br>
      </td>
      <td style="vertical-align: top;">2004-12-07<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">5.<br>
      </td>
      <td style="vertical-align: top;">RC to continue developing
planning infrastructure<br>
      </td>
      <td style="vertical-align: top;">RC<br>
      </td>
      <td style="vertical-align: top;">2004-12-07<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">6.<br>
      </td>
      <td style="vertical-align: top;">RC to mail BR the questions that
PR needs answered<br>
      </td>
      <td style="vertical-align: top;">RC<br>
      </td>
      <td style="vertical-align: top;">2004-11-24<br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;">7.<br>
      </td>
      <td style="vertical-align: top;"><span style="font-weight: bold;">Comments
to replace Notes</span><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">Need to be able to add
attachments to comments - probably each change delta could have an
attachment but most won't.<br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">Don't need explicit hyperlink
attachments, the text should be parsed for links and they should be
marked up accordingly.<br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
    <tr>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;">Need to show task history on the
main page, ie the state changes as well as comments so that you can
access the attachments and view history without looking at change log
for full audit.<br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
      <td style="vertical-align: top;"><br>
      </td>
    </tr>
  </tbody>
</table>
<br>
<table border="1" cellpadding="2" cellspacing="0" width="100%">
  <tbody>
    <tr>
      <th bgcolor="#cccccc" valign="top">Author<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Date<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Next Meeting<br>
      </th>
      <th bgcolor="#cccccc" valign="top">Venue<br>
      </th>
    </tr>
    <tr>
      <td valign="top">Robert Crida<br>
      </td>
      <td valign="top">2004-11-24<br>
      </td>
      <td valign="top">2004-12-07<br>
      </td>
      <td valign="top">13 Pearson Road<br>
      </td>
    </tr>
  </tbody>
</table>
<br>
</body>
</html>
